Shortcut management unit and method, and storage medium

ABSTRACT

A shortcut management device capable of improving user-friendliness of a portal application. The shortcut management device is capable of executing shortcuts which use functions of an electronic apparatus, and manages at least part of the functions used by the shortcuts. A storage unit registers shortcuts. An invalidation detecting unit detects that the license is invalidated. A retrieval unit retrieves a shortcut made inexecutable in association with the license of which the invalidation is detected. An invalidation unit invalidates the retrieved shortcut.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a shortcut management device which iscapable of executing a shortcut using a function of an electronicapparatus, and managing at least part of the function used through theshortcut, according to the license, and a shortcut management method.

2. Description of the Related Art

Recently, embedded devices have also been provided with an environmentwhich dynamically starts and stops an unspecified application to causethe same to operate therein. Under such a circumstance, an applicationhas been developed which manages a shortcut for calling the function ofthe unspecified application with particular settings. Here, theapplication for managing shortcuts is referred to as a portalapplication.

In general, this application has a function of displaying a list ofmanaged shortcuts on an operation screen. The application operates suchthat a user selects a desired shortcut and instructs the same to beexecuted, whereby another application is executed by a specific settingassociated with the shortcut. Here, the application actually called inassociation with the shortcut is referred to as a registeredapplication.

The shortcuts are required to be continuously managed. For example,there are cases where an application which is no longer required isdeleted, and a newly required shortcut is created. To save the effort ofmanaging these shortcuts, there has been proposed a portal applicationwhich is configured to automatically perform creation and deletion ofshortcuts (see Japanese Patent Laid-Open Publication No. 2002-259010).

Japanese Patent Laid-Open Publication No. 2002-259010 discloses aconfiguration in which if conditions predetermined by a registeredapplication for shortcut creation are satisfied, a shortcut associatedtherewith is automatically created, and if conditions predetermined bythe same for shortcut deletion are satisfied, the shortcut isautomatically deleted. As a specific example of the conditions forshortcut creation, the publication describes the number of times ofstarting of the registered application. Further, as a specific exampleof the conditions for shortcut deletion, the publication describes atime period during which the registered application is not started, anda ratio of the number of times of starting per a predetermined timeperiod. If the configuration described in Japanese Patent Laid-OpenPublication No. 2002-259010 is employed, it becomes unnecessary for auser to perform creation and deletion of shortcuts, and hence it canexpected to achieve advantageous effects of reduction of the managementcosts.

On the other hand, some registered applications provided in an embeddeddevice require licenses for respective operations of the applicationsthemselves, or part of the functions of the applications. The license ofeach application includes a type which permits the use of theapplication for a predetermined time period, or a type which permits theuse of the same until it is executed a predetermined number of times. Insuch a license, if a condition is not satisfied any longer, the licenseis invalidated, which makes unavailable the application or part of thefunctions thereof associated with the license.

However, the above-mentioned shortcut management device suffers from thefollowing problem: In the shortcut management device disclosed inJapanese Patent Laid-Open Publication No. 2002-259010, a first problemis that even if the license is invalidated, making unavailable theassociated application or part of the functions of the application, theshortcut remains for a while. This causes a problem that the portalapplication is not user-friendly during the time.

A second problem is that since no consideration is given to a case ofcreation of a shortcut by integrating settings for processing by aregistered application, it is difficult to automatically create theshortcut in which the settings are integrated. Therefore, it is requiredto reconfigure the settings for processing by the registered applicationassociated with the shortcut after the application is started via theshortcut. This makes the portal application not user-friendly.

A third problem is that since no consideration is given to a case ofcreation of a shortcut by integrating settings for processing by aregistered application, similarly to the second problem, even if part ofthe functions used by the registered application becomes unavailable,the proposed shortcut management device does not perform maintenance onthe shortcut. Therefore, the user has to take the trouble to manuallyedit or delete the shortcut. Further, the proposed shortcut managementdevice cannot cope with a case where the user desires to make use of theshortcut after eliminating part of the functions used by the registeredapplication.

SUMMARY OF THE INVENTION

The present invention provides a shortcut management device, a shortcutmanagement method, and a storage medium, which are capable of improvinguser-friendliness of a portal application.

In a first aspect of the present invention, there is provided a shortcutmanagement device which is capable of executing shortcuts which usefunctions of an electronic apparatus, and manages at least part of thefunctions used by the shortcuts according to a license, comprising astorage unit in which the shortcuts are registered, an invalidationdetecting unit configured to detect that the license is invalidated, aretrieval unit configured to retrieve a shortcut which is madeinexecutable in association with the license of which the invalidationis detected by the invalidation detecting unit, and an invalidation unitconfigured to invalidate the shortcut which is retrieved by theretrieval unit.

In a second aspect of the present invention, there is provided ashortcut management method for an electronic apparatus which is capableof executing shortcuts which uses functions of the electronic apparatus,and manages at least part of the functions used by the shortcutsaccording to a license, comprising causing the electronic apparatus todetect that the license is invalidated, causing the electronic apparatusto retrieve a shortcut which is made inexecutable in association withthe license of which the invalidation is detected by the detecting, andcausing the electronic apparatus to invalidate the shortcut which isretrieved by the retrieving.

In a third aspect of the present invention, there is provided acomputer-readable storage medium storing a program for causing acomputer to execute a shortcut management method for an electronicapparatus which is capable of executing shortcuts which use functions ofthe electronic apparatus, and manages at least part of the functionsused by the shortcuts according to a license, wherein the methodcomprises causing the electronic apparatus to detect that the license isinvalidated, causing the electronic apparatus to retrieve a shortcutwhich is made inexecutable in association with the license of which theinvalidation is detected by the detecting, and causing the electronicapparatus to invalidate the shortcut which is retrieved by theretrieving.

When a license is invalidated to make functions of the associatedelectronic apparatus unavailable, the shortcut management deviceaccording to the first aspect of the present invention immediately andautomatically invalidates the shortcut. This improves theuser-friendliness of the portal application. Further, according to theshortcut management method according to the second aspect of the presentinvention, it is also possible to obtain the same advantageous effectsas provided by the first aspect of the present invention.

Further features of the present invention will become apparent from thefollowing description of exemplary embodiments with reference to theattached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic block diagram of an image forming apparatus towhich a shortcut management device according to an embodiment of thepresent invention is applied.

FIG. 2 is a block diagram of various software units stored in arecording medium, such as an auxiliary storage device, in a controllersection.

FIG. 3 is a diagram showing a description of a shortcut file.

FIG. 4 is a diagram showing a shortcut definition file describingdetails of processes to be executed by a shortcut.

FIG. 5 is a diagram showing a specific example of a permanent license.

FIG. 6 is a diagram showing a specific example of a time-limitedlicense.

FIG. 7 is a diagram showing a description of a shortcut acquired as aresult of eliminating the setting of high-compression PDF.

FIG. 8 is a flowchart of a shortcut management process when a license isinvalidated.

FIG. 9 is a flowchart of a shortcut management process for detecting andinvalidating a time-limited license of which a range set thereto isexceeded.

FIG. 10 is a flowchart of a shortcut management process executed when alicense is validated.

FIG. 11 is a view showing an operation screen of a portal applicationwhen all the shortcuts are executable.

FIG. 12 is a view showing an example of the operation screen of theportal application when the license of a “Send” application as one ofbasic functions is invalidated.

FIG. 13 is a view showing an example of the operation screen of theportal application when the license of a “high-compression PDF” functionas one of partial functions equipped in the image forming apparatus 10is invalidated.

FIG. 14 is a block diagram of the minimum required various softwareunits.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The present invention will now be described in detail below withreference to the accompanying drawings showing embodiments thereof.

A description will be given of a shortcut management device according toan embodiment of the present invention with reference to the drawings.The shortcut management device according to the present embodiment isapplied to an image forming apparatus.

FIG. 1 is a schematic block diagram of an image forming apparatus towhich the shortcut management device according to the embodiment isapplied. The image forming apparatus 10 is comprised of a controllersection 101, a printer section 102, a reader section 103, and afacsimile (FAX) section 104.

The printer section 102 is configured to form an image on a sheet usingimage data. The reader section 103 is configured to read an original tocreate image data. The facsimile (FAX) section 104 is configured totransmit the read image data to a party on the other end over atelephone line.

The controller section (information processing apparatus) 101 controlsthe entire apparatus, and is connected to a client PC 140 via a LAN 130.Further, a CPU 110, a nonvolatile memory 111, a volatile memory 112, anauxiliary storage device 113, a display 114, an input device 115, and anetwork communication device 116 are connected to the controller section101 via an internal bus 120.

The CPU 110 is configured to execute programs to perform variousprocesses. The nonvolatile memory 111 forms a ROM. The nonvolatilememory 111 stores programs and data required for an initial stage of aprocess for starting the image forming apparatus 10. The volatile memory112 forms a RAM, and is used as a temporary storage area for programsand data.

The auxiliary storage device 113 is implemented by a mass-storagedevice, such as a hard disc, a RAM drive or the like, and stores largevolumes of data and execution codes of the programs. Further, theauxiliary storage device 113 stores data required to be held for longertime periods than data to be stored in the volatile memory 112, andhence stores various software units and shortcuts in the presentembodiment.

The display 114 is used for notifying information to a user using theimage forming apparatus 10. In the present embodiment, it is assumedthat the term “user” is always intended to mean the user of the imageforming apparatus 10. The input device 115 is used for receiving aselection or an instruction by the user, and transmitting the same to anassociated program via the internal bus 120. The network communicationdevice 116 is used for communicating with the other informationprocessing apparatuses via a network. It should be noted that thedisplay 114 and the input device 115 form an operation section 118 ofthe image forming apparatus 10.

As described above, the internal bus 120 is a communication bus thatcommunicably connects the CPU 110, the nonvolatile memory 111, thevolatile memory 112, the auxiliary storage device 113, the display 114,the input device 115, and the network communication device 116, to eachother, within the controller section 101.

The LAN 130 is a network which communicably connects the image formingapparatus 10 and the other information processing apparatuses. Theclient PC 140 is one of the other information processing apparatusescapable of communicating with the image forming apparatus 10 via the LAN130.

The configurations of the printer section 102, the reader section 103,and the facsimile (FAX) section 104 are known, and further are notdirectly related to the present invention, and hence detaileddescriptions thereof are omitted.

FIG. 2 is a schematic block diagram of various software units stored ina recording medium, such as the auxiliary storage device 113, in thecontroller section 101. As mentioned above, the sections implemented asthe various software units are stored in any of the storage media, suchas the nonvolatile memory 111, the volatile memory 112, and theauxiliary storage device 113, and are executed by the CPU 110. In thepresent embodiment, the various software units are broadly categorizedinto three: a portal application 220, registered applications 222(222-1, . . . , 222-N), and a license management system 221.

A shortcut-storing unit 201 of the portal application 220 storesshortcuts held by the controller section 101. The shortcuts are storedin the auxiliary storage device 113 as files. FIG. 3 is a diagramshowing a description of a shortcut file 301. The shortcut files 301 arecreated by the portal application 220 so as to manage shortcuts. Theshortcut managed by the shortcut file 301 is represented by a button tagin FIG. 3.

Further, details of description of processes of each shortcut aremanaged in another file (shortcut definition file). FIG. 4 is a diagramshowing a shortcut definition file describing details of processes to beexecuted by a shortcut. The description of the shortcut file 301 shownin FIG. 3A includes an ActID tag as link information. The shortcutdefinition file indicative of the details of processes to be executed bythe shortcut is uniquely identified by means of an ID set in this tag.That is, the ActID is used as information for uniquely identifying theshortcut.

In the description of the shortcut file 301, an application which isexecuted by the shortcut is indicated by an AppID tag. The applicationwhich is actually executed by the shortcut is uniquely identified bymeans of an ID set in this tag.

Further, an Alias tag indicates an application name. Further, a Name tagindicates the name of the shortcut. Further, a Comment tag indicates acomment given to the shortcut.

As shown in the shortcut file 301, the portal application manages eachshortcut by means of two IDs: AppID and ActID. That is, the portalapplication manages each shortcut such that an application to beexecuted by the shortcut is uniquely identified by AppID, and theshortcut to be executed is uniquely identified by ActID.

The description of the shortcut definition file (hereinafter simplyreferred to as the shortcut) 302 illustrated in FIG. 4 indicates detailsof processes to be executed by a registered application, which aredefined on a shortcut basis. The illustrated example shows a case wherea shortcut named as Shortcut 1 is formed in a file in XML format.

A Workflow tag includes an attribute ActID. This ActID is associatedwith the ActID mentioned in the foregoing description of the shortcutfile 301, and is for uniquely identifying the shortcut. The illustratedexample of the shortcut 302 defines a procedure of execution ofdouble-sided scanning on an original thereby converting the same tohigh-compressed and encrypted PDF data, and transmitting the data to anaddress “a@b.com”.

A shortcut registration unit 202 appearing in FIG. 2 registers ashortcut created by the controller section 101 in FIG. 1, by theshortcut-storing unit 201 appearing in FIG. 2. If a shortcut is newlyregistered, a shortcut file 301 in FIG. 3 and a shortcut (shortcutdefinition file) 302 in FIG. 4 are stored by the shortcut-storing unit201 for the registered shortcut.

In FIG. 2, a shortcut execution-instructing unit 203 for startingprocessing by a registered application according to the information ofthe shortcut. Since the actual processing is performed by the registeredapplication, the shortcut execution-instructing unit 203 triggersexecution of the registered application, and passing the settinginformation required for the processing to the registered application.

A shortcut-displaying unit 204 displays a list of shortcuts stored bythe shortcut-storing unit 201 and detailed information on each shortcut.By displaying the list and information on the display 114, it ispossible for the user to confirm the shortcuts, and perform an operationon each shortcut using the shortcut execution-instructing unit 203 orthe shortcut registration unit 202.

A license-storing unit 205 stores licenses associated with applicationsand partial functions of applications, which operate in the controllersection 101, and statuses of the licenses.

Now, a detailed description will be given of a license. The license isinformation for enabling the user of the image forming apparatus 10 touse at least one application or a partial function of an application.Further, the license is used for enabling the user to use a functionequipped in the image forming apparatus 10. If a license is obtainedi.e. validated, at least one associated application or partial functionthereof becomes available to the user. Inversely, if the license isinvalidated, the at least one associated application or partial functionthereof becomes unavailable to the user. When a license is in avalidated state, it will be expressed as “the license is valid”, whereaswhen a license is in an invalidated state, it will be expressed as “thelicense is invalid”. Further, each of these statuses are referred to asa license status. In the present embodiment, it is assumed that anapplication which becomes executable by obtaining the license is aregistered application 222. It should be noted that there are aplurality of registered applications 222 (222-1, . . . , 222-N), andthere are also a plurality of shortcut-executing units 219 (219-1, . . ., 219-N) in association with the respective registered applications. Theregistered applications in the present embodiment include “copy”,“print”, “scan”, and “Send” applications, which correspond to thefunctions of the image forming apparatus 10, respectively. It is assumedthat at least one of the applications is managed under license. Further,a specified function contained in one application may be managed underlicense. It should be noted that a description will be given of oneregistered application and one shortcut-executing unit, using therespective reference numerals 222 and 219 in the following description.The information on the license is stored in the auxiliary storagesection 113 in a text file. However, when a license is actuallyobtained, it is in an encrypted form so as to preventing an illegal useof the license, and the license is multiply-backed up. In the presentembodiment, a description will be given of a configuration in which thelicense is managed by only one file in an unencrypted state, by way ofexample.

Further, the license includes two types: a permanent license and atime-limited license (or limited license). If a permanent license isonce obtained i.e. validated, the associated application(s) or thepartial function thereof are made available on a permanent basis. FIG. 5is a diagram showing a specific example of the permanent license.

A permanent license 401 has three items of information: “LICENSE ID”402, “LICENSED FUNCTION ID” 403, and “LICENSED DEVICE ID” 404. The“LICENSE ID” 402 is an identifier for uniquely identifying this license.The “LICENSED FUNCTION ID” 403 is an identifier for identifying at leastone application or partial function of the same, associated with thisfile of the license. In FIG. 5, the “LICENSED FUNCTION ID” 403 isrealized by a UUID (Universal Unique Identifier) identifier. It shouldbe noted that in the present embodiment, the “LICENSED FUNCTION ID” 403corresponds to the AppID in FIGS. 3 and 4. Further, the “LICENSED DEVICEID” 404 is an identifier for identifying the image forming apparatus 10associated with this license file. In FIG. 5, the “LICENSED DEVICE ID”404 is realized by a UUID identifier.

On the other hand, in the time-limited license, a range in which thelicense is valid is set. Therefore, even if the license is oncevalidated, the associated application(s) or the partial function thereofis/are not made available on a permanent basis. If the range defined inthe license is exceeded, the license is automatically invalidated. Afterthe license is automatically invalidated, the associated application(s)or the partial function thereof become(s) unavailable. The range whichcan be set to the time-limited license and within which the license isvalid includes the following two types: A first type is defined byinformation indicative of a time period or the number of days duringwhich the associated application(s) or partial function thereof is/areavailable. A second type is defined by the number of times of execution,which is to be counted by a counter. The number of times of execution isthe number of times of starting an application associated with thelicense or the number of times of using the partial function of theapplication. Further, it is assumed that instead of the number of timesof execution, the number of times of operation of the printer section102, the reader section 103, or the facsimile section 104 of the imageforming apparatus 10 by the execution of the application may be counted.

FIG. 6 is a diagram showing a specific example of the time-limitedlicense. A time-limited license 501 has the following items ofinformation: “LICENSE ID” 502, “LICENSED FUNCTION ID” 503, “LICENSEDDEVICE ID” 504, and “LICENSE RANGE” 505.

The “LICENSE ID” 502, the “LICENSED FUNCTION ID” 503, and the “LICENSEDDEVICE ID” 504 respectively indicate the same items of information asthose in FIG. 5, and hence description thereof is omitted. The “LICENSERANGE” 505 indicates a range within which the license is valid. A “DATE”506 indicates a time period during which the license is valid. In theillustrated example in FIG. 6, the license is valid only during the timeperiod between “Jul. 1, 2008” and “Dec. 31, 2008”.

A “COUNT” 507 indicates the number of times of execution of theapplication(s) or the partial function thereof associated with thelicense. In the illustrated example in FIG. 6, the license is validuntil the application or the partial function, identified by the“LICENSED FUNCTION ID” 503, is used 1000 times. Further, in theillustrated example in FIG. 6, these conditions are combined by alogical operator. More specifically, the “DATE” 506 and the “COUNT” 507are combined by a logical operator “&”. This indicates that the licenseis valid only during a time period in which both of the conditions ofthe DATE” 506 and the “COUNT” 507 are satisfied.

A license registration unit 206 registers a license associated with atleast one application or partial function of the same which operate inthe controller section 101 of the image forming apparatus 10. Theregistration of the license is performed from the client PC 140connected via the LAN 130.

A license-deleting unit 207 deletes a license stored by thelicense-storing unit 205. The deleted license cannot be used in theimage forming apparatus 10 before the license is registered again by thelicense registration unit 206.

A license-validating unit 208 validates an invalidated one of licensesstored by the license-storing unit 205. As mentioned above, if thelicense is validated, at least one associated application or partialfunction of an application becomes available to the user.

A time-limited license-monitoring unit 209 monitors whether or not thereis a time-limited license of which the range set thereto is exceeded. Aspecific monitoring method is different depending on the type of rangeset to the time-limited license. In the present embodiment, adescription will be given assuming that a time period during which alicense is valid and the number of time of execution of at least oneapplication or partial function of the same with which the license isassociated are monitored in accordance with the illustrated example inFIG. 6.

Monitoring the time period during which the license is valid isperformed by comparing the current date and time held by the controllersection 101 of the image forming apparatus 10 with the informationdefined in the license. In the illustrated example in FIG. 6,information of a time period between “2008/07/01” and “2008/12/31” isstored, and the time-limited license-monitoring unit 209 continues tomonitor whether or not the current date and time is within the timeperiod.

Further, monitoring the number of times of execution of at least oneapplication or partial function of the same with which the license isassociated is performed by comparing the counter value of the number oftimes of execution with information defined in the license. In theillustrated example in FIG. 6, information of the number of 1000 timesis stored, and the time-limited license-monitoring unit 209 continues tomonitor whether or not the number of times of execution exceeds 1000times. It should be noted that a detailed flow of processing executed bythe time-limited license-monitoring unit 209 will be describedhereinafter with reference to FIG. 9.

A license-invalidating unit 210 invalidates a specific license in thevalidated status out of the licenses stored by the license-storing unit205. As described above, if a license is invalidated, at least oneassociated application or partial function of the same becomesunavailable to the user.

An invalid license-detecting unit 211 (invalidation-detecting unit)detects that a license is invalidated by the license-invalidating unit210. Specifically, the invalid license-detecting unit 211 checks anddetects statuses of all licenses stored by the license-storing unit 205.The invalid license-detecting unit 211 holds the statuses of alllicenses, and detects an invalidated license by determining thedifference between those statuses.

An associated shortcut retrieval unit 212 (searching unit) retrieves ashortcut associated with an invalidated license. The invalidated licenseis a license detected by the invalid license-detecting unit 211. Here, aphrase “associated with an invalidated license” is intended to refer toa state of a shortcut in which a license associated therewith isinvalidated and the shortcut becomes unable to be executed or has cometo produce a different result of execution thereof. Therefore, retrievedshortcuts are classified into two types: a type made inexecutable due toinvalidation thereof, and a type having come to produce a differentresult due to the same. Retrieval is performed on the shortcuts storedby the shortcut-storing unit 201.

For example, if the license of “Send” is invalidated, the shortcut 302(see FIG. 4) is detected as an associated shortcut. Further, theshortcut 302 is classified as the type made inexecutable due toinvalidation of the license. Further, if the license of thehigh-compression PDF is invalidated, the shortcut 302 is detected as anassociated shortcut. Further, the shortcut 302 is classified as the typehaving come to produce a different result due to invalidation of thelicense. On the other hand, if the license of a searchable PDF isinvalidated, the shortcut 302 is not detected as an associated shortcut.

A backup unit 213 stores a shortcut retrieved by the associated shortcutretrieval unit 212 in a manner distinguishable from shortcuts usuallyused. The retrieved shortcut is stored in a different area partitionedin the auxiliary storage device 113.

A function-eliminating unit 214 is eliminates a function which becomesunavailable from the shortcut. Here, a phrase “a function which becomesunavailable” is intended to mean a function associated with the licensedetected by the invalid license-detecting unit 211. Further, “eliminate”is intended to mean that only the function associated with theinvalidated license is eliminated by changing details of definition ofthe shortcut.

Further, the function-eliminating unit 214 performs processing on theshortcut which is classified as the type having come to produce adifferent result due to invalidation of the license out of shortcutsretrieved by the associated shortcut retrieval unit 212.

For example, if the license of the high-compression PDF is invalidated,the setting of the high compression PDF in association with the licenseof the high-compression PDF is eliminated from the shortcut 302. FIG. 7is a diagram showing a description of the shortcut which is obtained asa result of eliminating the setting of the high compression PDF. In ashortcut 601, “<high compression PDF> on </high compression PDF>” iseliminated from the shortcut 302 in FIG. 4.

A shortcut-deleting unit 215 is deletes an inexecutable shortcut. Here,“an inexecutable shortcut” is intended to mean a shortcut which isclassified as the type made inexecutable due to invalidation of thelicense out of shortcuts retrieved by the associated shortcut retrievalunit 212. Further, “deleting” includes invalidating a shortcut, such asdeleting a shortcut out of shortcuts stored by the shortcut-storing unit201, and making a shortcut inexecutable. That is, the shortcut-deletingunit 215 functions as means for invalidating a shortcut. It becomesimpossible to access the deleted shortcut thereafter.

A valid license-detecting unit 216 (validation detecting unit) detectsthat a license is validated by the license-validating unit 208.Specifically, the valid license-detecting unit 216 checks and detectsthe statuses of all licenses stored by the license-storing unit 205. Thevalid license-detecting unit 216 stores the statuses of all licenses,and determines a difference between the preceding statuses and thecurrent statuses to thereby detect a validated license.

An executable shortcut retrieval unit 217 (second searching unit)retrieves an executable shortcut out of shortcuts backed up by thebackup unit 213. For example, in a state where the license of the highcompression PDF is invalidated, the shortcut 302 in FIG. 4 is notretrieved. However, in a state where the license of the high compressionPDF is validated to make available all of the functions required forexecution of the shortcut 302, the shortcut 302 is retrieved.

A restoring unit 218 restores a shortcut retrieved by the executableshortcut retrieval unit 217 to a state stored by the shortcut-storingunit 201. The shortcut retrieved by the executable shortcut retrievalunit 217 has been stored by the backup unit 213, in a mannerdistinguishable from the shortcuts stored by the shortcut-storing unit201. The shortcut stored by the backup unit 213 is restored by therestoring unit 218 to the state stored by the shortcut-storing unit 201.Therefore, this makes it possible to display the shortcut by theshortcut-displaying unit 204, and execute the shortcut by the shortcutexecution-instructing unit 203.

The shortcut-executing unit 219 receives an instruction for executing ashortcut from the shortcut execution-instructing unit 203, and actuallyexecutes the shortcut.

The software units described above are provided in the portalapplication 220, the license management system 221, and the registeredapplication 222. More specifically, the portal application 220 includesthe shortcut-storing unit 201, the shortcut registration unit 202, theshortcut execution-instructing unit 203, the shortcut-displaying unit204, the associated shortcut retrieval unit 212, and the backup unit213. The portal application 220 also includes the function-eliminatingunit 214, the shortcut-deleting unit 215, the executable shortcutretrieval unit 217, and the restoring unit 218. Further, the licensemanagement system 221 includes the license-storing unit 205, the licenseregistration unit 206, the license-deleting unit 207, and thelicense-validating unit 208. The license management system 221 alsoincludes the time-limited license-monitoring unit 209, thelicense-invalidating unit 210, the invalid license-detecting unit 211,and the valid license-detecting unit 216. Further, the registeredapplication 222 (222-1, . . . , 222-N) includes the shortcut-executingunit 219 (219-1, . . . , 219-N).

FIG. 8 is a flowchart of a shortcut management process executed when alicense is invalidated. As describe above, this processing program isstored in one of the storage media, i.e. the nonvolatile memory 111, thevolatile memory 112, and the auxiliary storage device 113, in thecontroller section 101, and is executed by the CPU 110 in the controllersection 101. In the illustrated example, as a precondition, it isassumed that there is at least one application the license of which isvalid, and the license is stored by the license-storing unit 205.

The controller section 101 invalidates the license of a application bythe license-invalidating unit 210 (step S1). In invalidating thelicense, the user gives an instruction for invalidating the license ofthe application selected by the user through the input device 115according to contents displayed on the display 114. When the inputdevice 115 receives the instruction for invalidating the license fromthe user, the input device 115 transmits the accepted instruction to thelicense-invalidating unit 210. Upon reception of the acceptedinstruction by the license-invalidating unit 210, the controller section101 invalidates the license associated with the application stored bythe license-storing unit 205. Alternatively, when the valid period ofthe time-limited license expires, the license-invalidating unit 210invalidates the time-limited license.

The controller section 101 detects using the invalid license-detectingunit 211 that the license is invalidated (step S2). Thus, theinvalidated license is detected.

Using the associated shortcut retrieval unit 212, the controller section101 retrieves a shortcut which is associated with the application thelicense of which is invalidated (step S3). Specifically, by referring toa license as illustrated in FIG. 5, the controller section 101identifies the AppID of the application the license of which isinvalidated. Then, a shortcut file 301 illustrated in FIG. 3 isretrieved which contains ActID described in association with theidentified AppID. This retrieves the shortcut associated with theinvalidated license.

The controller section 101 determines using the backup unit 213, whetheror not a shortcut is detected as a result of retrieval in the step S3(step S4). If no shortcut is detected, the controller section 101terminates the present process.

On the other hand, if at least one shortcut is detected, the controllersection 101 backs up the shortcut retrieved in the step S3 using thebackup unit 213 (step S5).

The controller section 101 determines whether or not the shortcut isexecutable even after the application or partial function thereofassociated with the license invalidated in the step S1 is eliminated bythe function-eliminating unit 214 from the shortcut detected in the stepS3 (step S6). If the shortcut is executable, the controller section 101causes the function-eliminating unit 214 to eliminate the application orpartial function thereof associated with the license invalidated in thestep S1, from the shortcut (step S7). The phrase “if the shortcut isexecutable” is intended to mean the aforementioned case where theshortcut is classified as “the type having come to produce a differentresult due to invalidation of the license”. On the other hand, if theshortcut is inexecutable, the controller section 101 causes theshortcut-deleting unit 215 to delete the shortcut (step S8). The phrase“if the shortcut is inexecutable” is intended to mean the case where theshortcut is classified as “the type made inexecutable due toinvalidation of the license”.

After executing the steps S7 and S8, the controller section 101determines whether or not the step S6 and subsequent steps are executedon all of the shortcuts retrieved in the step S3 (step S9). If the stepS6 and subsequent steps have been executed on all of the shortcuts, thecontroller section 101 terminates the present process executed when thelicense is invalidated. On the other hand, if the step S6 and subsequentsteps have not been executed on all of the shortcuts, the controllersection 101 returns to the step S6.

FIG. 9 is a flowchart of a shortcut management process executed when atime-limited license of which the range set thereto is exceeded isdetected and invalidated. As described above, this processing is storedin one of the storage media, i.e. the nonvolatile memory 111, thevolatile memory 112, and the auxiliary storage device 113, in thecontroller section 101, and is executed by the CPU 110 in the controllersection 101. It should be noted that as described hereinafter,processing after detecting the license of which the range set thereto isexceeded is similar to that in FIG. 8. In the illustrated example, it isassumed as a precondition that at least one validated time-limitedlicenses exists, and is stored by the license-storing unit 205.

The controller section 101 acquires all information on time-limitedlicenses stored by the license-storing unit 205, using the time-limitedlicense-monitoring unit 209, and makes a list of them (step S11).Hereinafter, this list is referred to as the time-limited license list.

The controller section 101 determines, using the time-limitedlicense-monitoring unit 209, whether or not checking of all licenses inthe time-limited license list acquired in the step S11 as to expirationof a valid time period is completed (step S12). If the checking of alllicenses in the time-limited license list acquired in the step S11 iscompleted, or if the time-limited license list acquired in the step S11is empty, the controller section 101 proceeds to a step S17.

On the other hand, if the checking of all licenses in the time-limitedlicense list acquired in the step S11 is not completed, the controllersection 101 performs the following processing: The controller section101 checks a time-limited license in the time-limited license list,which remains to be checked, using the time-limited license-monitoringunit 209, to determine whether or not the valid time period of thetime-limited license has expired (step S13).

What is checked here is whether or not the current date and time iswithin the range defined in the time-limited license during which thelicense is valid. If the current date and time is within the rangedefined in the time-limited license during which the license is valid,the controller section 101 returns to the step S12.

On the other hand, if the current date and time is not within the rangedefined in the time-limited license during which the license is valid,the controller section 101 temporarily stores using the time-limitedlicense-monitoring unit 209 that the condition defined in thetime-limited license as to the time period during which the license isvalid is not satisfied (step S14).

The controller section 101 determines using the time-limitedlicense-monitoring unit 209, whether or not the conditions defined inthe time-limited license are satisfied (step S15). In thisdetermination, all of the conditions, including logical operators,defined in the time-limited license are determined. In the case of theexample illustrated in FIG. 6, the controller section 101 determineswhether or not there are satisfied both of the two conditions, i.e. thecondition as to the time period during which the license is valid andthe condition as to the number of times of execution of the applicationor the partial function of the same associated with the license.

As a result of the determination, if the conditions defined in thetime-limited license are satisfied, the controller section 101 returnsto the step S12. On the other hand, if the conditions defined in thetime-limited license are not satisfied, the controller section 101causes the license-invalidating unit 210 to invalidate the time-limitedlicense (step S16). The process in the step S16 is as described withreference to the flowchart in FIG. 8.

On the other hand, if it is determined in the step S12 that the checkingof all licenses in the time-limited license list is completed or if thetime-limited license list acquired in the step S11 is empty, thecontroller section 101 performs the following processing: The controllersection 101 determines using the time-limited license-monitoring unit209, whether or not the checking of all licenses in the time-limitedlicense list acquired in the step S11 as to the number of times ofexecution of an application or a partial function of the same associatedwith each license is completed (step S17).

If the checking of all the licenses as to the number of times ofexecution is completed, the controller section 101 terminates thepresent process. This includes the following two cases: One is the casewhere the checking of all licenses in the time-limited license listacquired in the step S11 as to the number of times of execution of anapplication or a partial function of the same associated with eachlicense is completed. The other is the case where the time-limitedlicense list acquired in the step S11 is empty.

On the other hand, if it is determined in the step S17 that the checkingof all licenses in the time-limited license list as to the number oftimes of execution of an application or a partial function of the sameassociated with each license is not completed, the controller section101 performs the following processing: Using the time-limitedlicense-monitoring unit 209, the controller section 101 checks atime-limited license in the time-limited license list which has not beenchecked yet, and determines based on a result of the checking whether ornot an upper limit value of the number of times of execution defined inthe time-limited license is smaller than the counter value (step S18).What is checked here is whether or not the counter value of the numberof times of execution exceeds the upper limit value of the number ofexecution of the application or the partial function of the same,associated with the license, which is defined in the time-limitedlicense.

If the counter value of the number of times of execution does not exceedthe upper limit value of the number of times of execution of theapplication or the partial function of the same, associated with thelicense, which is defined in the time-limited license, the controllersection 101 returns to the step S17. On the other hand, if the countervalue of the number of times of execution exceeds the upper limit valueof the number of times of execution of the application or the partialfunction of the same, associated with the license, which is defined inthe time-limited license, the controller section 101 performs thefollowing processing: The controller section 101 temporarily storesusing the time-limited license-monitoring unit 209 that the condition asto the number of times of execution of the application or the partialfunction of the same, associated with the license, which is defined inthe time-limited license, is not satisfied (step S19).

Using the time-limited license monitoring section 209, the controllersection 101 determines whether or not the conditions defined in thetime-limited license are satisfied (step S20). In this determination,all of the conditions, including the logical operators, defined in thetime-limited license are determined. In the case of the exampleillustrated in FIG. 6, the controller section 101 determines whether ornot there are satisfied both of the two conditions, i.e. the conditionas to the time period during which the license is valid, and thecondition as to the number of times of execution of the application orthe partial function of the same associated with the license.

As a result of the determination, if both of the conditions defined inthe time-limited license are satisfied, the controller section 101returns to the step S17. On the other hand, if both of the conditionsset to the time-limited license are not satisfied, the controllersection 101 causes the license-invalidating unit 210 to invalidate thetime-limited license (step S21). The processing in the step S21 is asdescribed hereinabove with reference to the flowchart in FIG. 8.Thereafter, the controller section 101 returns to the step S17.

By executing the flowcharts in FIGS. 8 and 9, it is possible for theimage forming apparatus 10 to refuse a instruction for executing theapplication the license of which is invalidated. Further, a shortcut isdeleted by determining whether or not the shortcut is executable evenafter the partial function of the application is made unavailable due toinvalidation of the license. This makes it possible to prevent theexecutable shortcut from being unnecessarily deleted.

FIG. 10 is a flowchart of a shortcut management process executed when alicense is validated. This processing program is stored in one of thestorage media, i.e. the nonvolatile memory 111, the volatile memory 112,and the auxiliary storage device 113, and is executed by the CPU 110. Inthe illustrated example, it is assumed as a precondition that at leastone invalidated time-limited license exists, and is stored by thelicense-storing unit 205.

The controller section 101 detects using the valid license-detectingunit 216 that a license is validated (step S51). The controller section101 retrieves an executable shortcut by the executable shortcutretrieval unit 217 out of the shortcuts backed up by the backup unit 213(step S52).

The controller section 101 determines using the restoring unit 218,whether or not there is at least one shortcut obtained as a result ofretrieval in the step S52 (step S53). If there is no shortcut obtainedas the result of retrieval, the controller section 101 terminates thepresent process.

On the other hand, as the result of retrieval in the step S52, if thereis at least one shortcut, the controller section 101 causes therestoring unit 218 to restore (reregister) the shortcut obtained as theresult of retrieval in the step S52 (step S54). That is, the backed-upshortcut is stored again in the original storage location. After thisstep, the controller section 101 terminates the process executed whenthe license is validated.

By executing the flowchart in FIG. 10, the shortcut transferred to thebackup area due to invalidation of the license becomes available againwhen the license is validated.

Next, a description will be given of an example of an operation screenof the portal application, which is displayed on the display 114 of theoperation section 118 with reference to FIGS. 11 to 13. FIG. 11 is aview showing an operation screen of the portal application displayedwhen all the shortcuts are executable. A screen 1101, which is the wholeoperation screen of the portal application 220, is displayed on thedisplay 114. Various buttons are set on the screen 1101.

A my button 1102 is used only for displaying a shortcut which isregistered by the user who uses the image forming apparatus 10. A groupbutton 1103 is used for displaying a shortcut which is mutuallyavailable to all of the users who use the image forming apparatus 10.

Buttons 1104 to 1118 are each used for instructing execution of ashortcut associated with a button. A button 1119 is used for instructingdeletion of a selected one of the registered shortcuts. A button 1120 isused for instructing edition of a selected one of the registeredshortcuts.

FIG. 12 is a view showing an example of the operation screen of theportal application when the license of the “Send” application as one ofthe basic functions is invalidated. By executing the step S8 of theflowchart in FIG. 8, the buttons 1106, 1107, 1109, 1111, 1112, and 1114to 1117, which become unavailable, are automatically deleted. Then,buttons 1301 to 1309 in an unregistered state are displayed in agrayed-out state. The display area of each of the buttons 1301 to 1309may be configured not to contain anything.

FIG. 13 is a view showing an example of the operation screen of theportal application displayed when the license of the “high-compressionPDF” function as one of the partial functions equipped in the imageforming apparatus 10 is invalidated. On this screen, buttons 1501 and1502 are associated with shortcuts resulting from deletion of thefunction of high compression PDF from the respective shortcutsassociated with the buttons 1106 and 1115 in FIG. 11. Further, toindicate this fact, a triangular icon is given to each of the buttons1501 and 1502. The addition of the triangular icon to each of thebuttons makes it possible to notify the user that part of the functionsof the shortcut is unavailable. A button to which the triangular icon isgiven may be configured such that when it is clicked, a screenindicating what partial function is made unavailable is displayed beforeexecuting image-processing set by the shortcut associated with theclicked button. This screen makes it possible for the user to recognizewhat partial function is unavailable. Then, being aware that the partialfunction is unavailable, the user may instruct to execute or not toexecute the shortcut.

As described above, according to the image forming apparatus of theembodiment, it is possible to improve user-friendliness of the portalapplication. That is, if a license is invalidated to make the associatedapplication or the partial function thereof unavailable, it is possibleto immediately and automatically delete a shortcut or shortcutsassociated therewith. This makes it possible to improveuser-friendliness of the portal application. Further, if the license isvalidated, it is possible to automatically create the formerly-usedshortcut(s). Therefore, it is not necessary to reconfigure the presetvalues for processing by the registered application which is registeredin the shortcut(s), and this also makes it possible to improveuser-friendliness of the portal application. Further, if a partialfunction to be used by a registered application is made unavailable, itis possible to automatically create a shortcut by eliminating thepartial function to be used by the registered application. This alsomakes it possible to improve user-friendliness of the portalapplication.

Further, if a shortcut is executable even after a partial function to beused by a shortcut is made unavailable, this shortcut is not deleted.This makes it possible to improve user-friendliness of the portalapplication.

Further, it is possible to easily register and delete a license.Further, it is possible to easily register a shortcut. Further, it ispossible to easily invalidate a license. Further, if a valid range setto a license is exceeded, it is possible to immediately invalidate thelicense. Further, it is possible to easily validate the license.

Further, buttons associated with respective shortcuts are arranged onthe screen of the portal application. This makes it possible to improveoperability when executing any of the shortcuts.

It should be noted that the units implemented by the respective softwaremodules in the above-described embodiment may be realized by otherconfigurations. Specifically, the license in the above-describedembodiment may store information other than the above-describedinformation. For example, the license may hold information of anidentifier of a licensed user. In this case, users other than thelicensed user of the license cannot use the license. Further, thelicense may hold information indicative of the status of the license.Inversely, the “LICENSED DEVICE ID” 404 may not be held in theabove-mentioned information (see FIG. 5).

Further, the time-limited license in the above-described embodimentemploys two ranges within which the license is valid, i.e. the timeperiod during which the license is valid, and the number of times ofexecution of an application or a partial function of the same,associated with the license. However, the range within which a licenseis valid may be otherwise specified. For example, information specificto an application or a partial function of the same associated with thelicense, such as the number of read sides of originals or the number ofsides subjected to printing, or the number of jobs, may be specified.Alternatively, a value indicative of a data size may be specified. Forexample, information indicative of a data size or a packet size, whichis processed by the application or the partial function of the sameassociated with the license, may be specified. Alternatively, the numberof simultaneous users who are simultaneously using the application orthe partial function may be specified. For example, the number of thesimultaneous users may be restricted, like a floating license. However,the number of simultaneous users is changed on a real time basis, andhence the backup unit 213 and the restoring unit 218 may be configurednot to manage the shortcut each time the number of simultaneous users ischanged. It should be noted that if the configuration of the rangewithin which the license is valid is changed to any described here, itis necessary to change the processing by the time-limitedlicense-monitoring unit 209 according to the change of theconfiguration. The operation of the time-limited license-monitoring unit209 will be described hereinafter.

Further, in the above-described embodiment, it is assumed that the rangeof the time-limited license within which it is valid can be determinedby combining a plurality of conditions using logical operators. Althoughin the illustrated example in FIG. 6, only “&” is mentioned, othergenerally-used logical operators may be used as well. For example, therange within which the license is valid may be determined by logicaladdition (or) of the conditions to each other by using “|”.Alternatively, the range may be determined by negation of the conditionswith using “̂”.

Further, the shortcut-storing unit 201 stores shortcuts in the auxiliarystorage device 113 as files. However, the area and the format forstoring the shortcuts may be differently configured. For example, theshortcuts may be stored in a database. Alternatively, the shortcuts maybe stored in a storage medium included in the other informationprocessing apparatus on the LAN 130 via the network communication device116. Alternatively, the shortcuts may be each stored in a CSV file or abinary file, not in an XML file.

Further, information held by a shortcut may not be the same as that heldby the shortcut 302. For example, an application may be started withoutsettings for the operation. Further, there may not be a plurality ofapplications to be operated. Further, one application may be repeatedlyoperated. Further, the information may contain character strings fordescription as an attribute of the shortcut.

Further, although in the above-described embodiment, the description isgiven of the configuration that both of the shortcut files 301 and theshortcuts 302 are stored by the shortcut-storing unit 201, this is notlimitative. For example, the shortcut files 301 may be stored by theshortcut-storing unit 201, and the shortcuts 302 may be stored inanother storage unit provided in the registered application 222.

Further, in the above-described embodiment, the shortcut registrationunit 202 creates a shortcut on the controller section (informationprocessing apparatus) 101 of the image forming apparatus 10, andregisters the shortcut by the shortcut-storing unit 201. However, theshortcut may be created in another place. For example, the shortcut maybe created on the other information processing apparatus, and input tothe information processing apparatus 101 of the image forming apparatus10 from the outside.

Further, the license registration unit 206 in the above-describedembodiment is not an essential component. For example, all the licenseinformation may be stored by the license-storing unit 205 in an invalidstate in advance. In this case, the license-deleting unit 207 is alsonot an essential component.

Further, the license-validating unit 208 in the above-describedembodiment is not an essential component. For example, the license maybe forcibly validated when the license is registered by the licenseregistration unit 206. In this case, it is not necessary for the licenseto have status information, and if the license is stored by thelicense-storing unit 205, the application or the partial functionthereof associated with the license becomes available. Similarly, thelicense-invalidating unit 210 is not an essential configuration.

Further, the time-limited license-monitoring unit 209 in theabove-described embodiment is required to change processes to beexecuted by a shortcut according to information on a range set to atime-limited license within which the license is valid. Here, adescription will be given of an operation of the time-limitedlicense-monitoring unit 209 which is configured to be compatible withthe setting of the time-limited license.

First, a description will be given of monitoring of information specificto the application or partial function of the same associated with thelicense. The registered application per se manages a specific countervalue, and performs counting up or down thereof, as required.Identification information and an upper limit value of the counter valueare described in the time-limited license. The time-limitedlicense-monitoring unit 209 refers to the counter based on theidentification information of the counter value, and performs monitoringby comparing the counter value with the upper limit value.

Next, a description will be given of monitoring of the amount of data orpackets which are processed by the application or the partial functionof the same associated with a license. A registered application is newlyprovided with means for measuring the amount of data or packets, andsets the measured value to a specific counter. IdentificationInformation and the upper limit value of the counter value are describedin the time-limited license. The time-limited license-monitoring unit209 refers to the counter based on the identification information of thecounter value, and performs monitoring by comparing the counter valuewith the upper limit value.

Next, a description will be given of monitoring of the number ofsimultaneous users who are simultaneously using the application or thepartial function of the same associated with the license. As describedabove, the number of simultaneous users is changed on a real time basis,and hence the backup unit 213 and the restoring unit 218 may beconfigured not to manage the shortcut each time the number of thesimultaneous users is changed. In this case, only for the restrictingcondition based on the number of simultaneous users, control isperformed so as not to cause the time-limited license-monitoring unit209 to carry out the detection.

Further, the backup unit 213 in the above-described embodiment storesthe shortcuts retrieved by the associated shortcut retrieval unit 212 ina manner distinguishable from the shortcuts usually used. Here, althoughin the description given hereinabove, the phrase “in a mannerdistinguishable” implies storing in another partition in the auxiliarystorage device 113, the retrieved shortcuts may be made distinguishablein a different manner. For example, the retrieved shortcuts may bestored in another directory within one partition. Alternatively, theretrieved shortcuts may each have a flag indicative of a shortcut backedup within one partition. Alternatively, another storage device may beprovided. Alternatively, the retrieved shortcuts may be stored in astorage medium provided in the other information processing apparatus onthe LAN 130.

Further, although the function-eliminating unit 214 in theabove-described embodiment eliminates an unavailable function from theshortcut, the function-eliminating unit 214 may be configured to furtherimprove the usability. For example, a message describing a functioneliminated by the function-eliminating unit 214 may be displayed on thedisplay 114 as an explanation of the shortcut. Alternatively, toindicate that an unavailable function is eliminated by thefunction-eliminating unit 214, a special mark may be attached to thename of the corresponding shortcut.

Further, the function-eliminating unit 214 in the above-describedembodiment is not an essential configuration. In the configurationwithout the function-eliminating unit 214, all of the shortcutsretrieved by the associated shortcut retrieval unit 212 are deleted bythe shortcut-deleting unit 215.

Further, the restoring unit 218 in the above-described embodimentrestores a shortcut retrieved by the executable shortcut retrieval unit217 to the state stored by the shortcut-storing unit 201. At this time,a particular determination may be carried out so as to actuallyreregister (restore) only a necessary one. For example, in a case wherereregistration (restoration) of a shortcut results in a plurality ofshortcuts defining the same processes, the shortcut may be detected inadvance for elimination from shortcuts to be restored. This makes itpossible to prevent a plurality of shortcuts defining the same processesfrom being created.

Further, if a shortcut remains from which an unavailable function iseliminated by the function-eliminating unit 214, the shortcut may beautomatically deleted at the time of restoring the shortcut. In thiscase, it is required to give each shortcut an identifier for uniquelyidentifying the shortcut. This makes it possible to prevent a pluralityof shortcuts defining the same processes from being created.

Further, when a shortcut remains from which an unavailable function iseliminated by the function-eliminating unit 214, if the shortcut is usedmore frequently than a predetermined frequency, the shortcut may not beautomatically deleted. In this case, a profile section for determiningthe frequency of use of each shortcut is necessary. This makes itpossible to improve operability without deleting the shortcut frequentlyused.

As described above, not all of the software units in the above-describedembodiment are essential. FIG. 14 is a block diagram of the minimumrequired various software units. Compared with FIG. 2, the licenseregistration unit 206, the license-deleting unit 207, the shortcutregistration unit 202 and the like are omitted from the configuration inFIG. 2.

It should be noted that the present invention is not limited to theconfiguration of the above-described embodiment, but any suitableconfiguration may be employed insofar as the configuration is capable ofrealizing the functions as described in claims, or the functionsequipped in the configuration of the present embodiment.

For example, although in the above-described embodiment, the case wherethe present invention is applied to the image forming apparatus isdescribed, this is not limitative, but the present invention can beapplied to various electronic apparatus.

Further, the present invention may be applied to a system comprised of aplurality of devices, or an apparatus implemented by one device.Further, it is to be understood that an image forming apparatus may be afacsimile device having a print function, or a multi-function peripheral(MFP) having a print function, a copy function, a scan function, and thelike, in addition to a printing device.

Further, it is to be understood that the processes of the presentinvention can be realized by causing a processing apparatus (CPU,processor) such as a personal computer or the like to execute software(programs) acquired via a network or various storage media.

Aspects of the present invention can also be realized by a computer of asystem or apparatus (or devices such as a CPU or MPU) that reads out andexecutes a program recorded on a memory device to perform the functionsof the above-described embodiment(s), and by a method, the steps ofwhich are performed by a computer of a system or apparatus by, forexample, reading out and executing a program recorded on a memory deviceto perform the functions of the above-described embodiment(s). For thispurpose, the program is provided to the computer for example via anetwork or from a recording medium of various types serving as thememory device (e.g., computer-readable medium).

While the present invention has been described with reference toexemplary embodiments, it is to be understood that the invention is notlimited to the disclosed exemplary embodiments. The scope of thefollowing claims is to be accorded the broadest interpretation so as toencompass all such modifications and equivalent structures andfunctions.

This application claims the benefit of Japanese Patent Application No.2009-035401, filed Feb. 18, 2009, which is hereby incorporated byreference herein in its entirety.

1. A shortcut management device which is capable of executing shortcutswhich use functions of an electronic apparatus, and manages at leastpart of the functions used by the shortcuts according to a license,comprising: a storage unit in which the shortcuts are registered; aninvalidation detecting unit configured to detect that the license isinvalidated; a retrieval unit configured to retrieve a shortcut which ismade inexecutable in association with the license of which theinvalidation is detected by said invalidation detecting unit; and aninvalidation unit configured to invalidate the shortcut which isretrieved by said retrieval unit.
 2. The shortcut management deviceaccording to claim 1, further comprising: a backup unit configured tostore the shortcut retrieved by said retrieval unit in a mannerdistinguishable from executable ones of the shortcuts which areregistered in said storage unit; a validation detecting unit configuredto detect that the license is validated; a second retrieval unitconfigured to retrieve a shortcut which is made executable inassociation with the license of which the validation is detected by saidvalidation detecting unit, from the shortcuts stored by said backupunit; and a reregistration unit configured to reregister the shortcutwhich is retrieved by said second retrieval unit onto said storage unit.3. The shortcut management device according to claim 1, furthercomprising a function eliminating unit configured to eliminate afunction associated with the invalidated license out of functions whichare used by the shortcut retrieved by said retrieval unit, wherein ifthe shortcut retrieved by said retrieval unit becomes inexecutable byeliminating the function by said function eliminating unit, saidinvalidation unit invalidates the shortcut.
 4. The shortcut managementdevice according to claim 3, wherein in a case where the shortcutretrieved by said retrieval unit is executable even after the functionis eliminated by said function eliminating unit, said invalidation unitdose not invalidate the shortcut.
 5. The shortcut management deviceaccording to claim 1, further comprising: a license invalidating unitconfigured to invalidate the license; and a monitoring unit configuredto monitor whether or not a valid range set to the license is exceeded,wherein if the valid range of the license is exceeded, said licenseinvalidating unit invalidates the license.
 6. The shortcut managementdevice according to claim 1, further comprising: a display unitconfigured to display buttons on a screen in association with theshortcuts which are registered by said storage unit, respectively; andan execution instructing unit configured to instruct execution of aselected one of the shortcuts associated with the buttons displayed onthe screen.
 7. The shortcut management device according to claim 2,wherein if it is detected that the shortcut to be reregistered hasalready been registered in said storage unit, said reregistration uniteliminates the shortcut from shortcuts to be reregistered.
 8. Theshortcut management device according to claim 2, further comprising afunction eliminating unit configured to eliminate a function associatedwith the invalidated license out of the functions used by the shortcutretrieved by the retrieval unit, wherein if it is detected that theshortcut to be reregistered, of which the function is eliminated by saidfunction eliminating unit, has already been registered in said storageunit, said reregistration unit eliminates the shortcut from shortcuts tobe reregistered.
 9. The shortcut management device according to claim 8,wherein even if it is detected that the shortcut to be reregistered, ofwhich the function is eliminated by said function eliminating unit, hasbeen registered in said storage unit, if frequency of usage thereof ishigher than a predetermined frequency, said reregistration unit does noteliminate the shortcut from the shortcuts to be reregistered.
 10. Ashortcut management method for an electronic apparatus which is capableof executing shortcuts which uses functions of the electronic apparatus,and manages at least part of the functions used by the shortcutsaccording to a license, comprising: causing the electronic apparatus todetect that the license is invalidated; causing the electronic apparatusto retrieve a shortcut which is made inexecutable in association withthe license of which the invalidation is detected by said detecting; andcausing the electronic apparatus to invalidate the shortcut which isretrieved by said retrieving.
 11. A computer-readable storage mediumstoring a program for causing a computer to execute a shortcutmanagement method for an electronic apparatus which is capable ofexecuting shortcuts which use functions of the electronic apparatus, andmanages at least part of the functions used by the shortcuts accordingto a license, wherein the method comprises: causing the electronicapparatus to detect that the license is invalidated; causing theelectronic apparatus to retrieve a shortcut which is made inexecutablein association with the license of which the invalidation is detected bysaid detecting; and causing the electronic apparatus to invalidate theshortcut which is retrieved by said retrieving.